Wanted to double-check that you want me to remove DateRange as it will be a more significant undertaking than the other ones. In addition to being available at the base of the API, it's used throughout the codebase, so I'll have to refactor all that too. Not a problem to do, but wanted to double-check before doing so.

can certainly leave that for now
but do it a separate pr if u can
it's just really a name for DatetimeIndex

FYI also need to check/update vbenches for any of these deprs

Not sure what the vbenches are? Is that what's in the vb_suite directory?

If so, here are the two places with FutureWarning

• https://github.com/pydata/pandas/blob/master/vb_suite/test_perf.py#L601
• https://github.com/pydata/pandas/blob/master/vb_suite/perf_HEAD.py#L92

You don't want me to delete those do you?

@jsexauer - let's leave out deprecating DateRange for another issue so we can make this a minor change that we can accept. If it's still used within pandas and on the vbenches, it doesn't really feel like DateRange is deprecated.

i.e. you can just open a separate PR that handles the refactor and deprecation for DateRange.

Ok I will do the DateRange one next. Just made a small change I saw in updating the docs (shouldn't affect tests). I think this one is ready for closing; let me know if more work is needed.

can you edit #6581 to update the >= 0.12 (that we are going to deprecate in the future)?

thanks

anyone have a problem with any of this, these are all removed deprecations that were in effect <= 0.11 (so a while ago). That were announced to be removed in a future version.

@jsexauer @jtratner @jorisvandenbossche @TomAugspurger @cpcloud @hayd @wesm

Looks good, but I don't see the html.py removal listed in the task list.

@cpcloud It is the second to last item in the "Deprecated since 0.12" list. I see that the warning message says to remove in 0.14, but warning was given only in 0.13. Let me know if you want me to remove anyways.

oh ok ... you're right ... sorry i haven't looked at html stuff in a while, carry on

yep....only doing < 0.12 announced deprecations (which their are a lot!)

I'm pretty wary of removing load and save since they're used in The Book. I'm not sure if any of these other deprecation will affect the book but should try to avoid if possible, I guess.

save/load not on the table as those where from. 0.12

@jsexauer in the list can u out the version that the depr happened (I know I have the commit but for reference) thanks

@wesm I don't own a copy of The Book unfortunately, but assuming it was written for v0.9 (given publish in Oct 2012) the only two of these that might affect it are

• the removal of the unique keyword from HDFStore.select_column
• deprecation of name in favor of symobls in pandas.io.data.get_data_yahoo and pandas.io.data.get_data_google

Do you know if either of these were used?

@jreback Modified inital PR comment to include versions of first deprecation. Also moved all deprecations not pulled out in this PR into #6581.

Neither of those are used in wes' book.

yep...i think this is all fine.

thanks @jsexauer

@jsexauer ok..this is merged, but can you do a follow up fix the issues in v0.14.0 (and prob in release.rst), so that they are the original issues numbers (and not the deprecation issue).

http://pandas-docs.github.io/pandas-docs-travis/whatsnew.html#whatsnew-0140-prior-deprecations

e.g. if you are looking thru that page you want to be able to click thru and see what the original issue was.

What should I do for the ones that that didn't have issues?

if u have a commit reference then u can use that (though u may have to do an inline reference)
if u can get it to work great if leave the existing referemce

Have an example you could point me to?

oh...looking in cookbook.rst, its just another external link. (The issues render differently/automatically, via the issue number), but a commit is just a reference like any other HTML link.